-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set specific awsClusterRoleIdentityName for CAPA test suites #444
Conversation
Note As this is a draft PR no triggers from the PR body will be handled. If you'd like to trigger them while draft please add them as a PR comment. |
76688e1
to
6cc67ce
Compare
Note As this is a draft PR no triggers from the PR body will be handled. If you'd like to trigger them while draft please add them as a PR comment. |
/run cluster-test-suites |
🤦 This is going to fail. |
/run cluster-test-suites TARGET_SUITES=./providers/capa,./providers/eks |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
/run cluster-test-suites TARGET_SUITES=./providers/capa/private,./providers/capa/cilium-eni-mode |
/run cluster-test-suites TARGET_SUITES=./providers/capa/private |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
COME ON!!!! 😞 /run cluster-test-suites TARGET_SUITES=./providers/capa/private |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
It turns out the capa private test suite is failing due to a missing IAM permission on the role in the new AWS account. Team Phoenix is assisting with getting it resolved and then I'll re-run the tests to confirm. |
/run cluster-test-suites TARGET_SUITES=./providers/capa/private |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
/run cluster-test-suites TARGET_SUITES=./providers/capa/private |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
/run cluster-test-suites TARGET_SUITES=./providers/capa/private |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
It looks like the private CAPA WCs don't currently work when deployed into a different AWS account. I've opened an issue for Team Phoenix to investigate and will be removing the change for private WCs from this PR so we can at least have the others isolated. Issue: giantswarm/roadmap#3671 |
Signed-off-by: Marcus Noble <[email protected]>
77f9689
to
bde6f2f
Compare
/run cluster-test-suites TARGET_SUITES=./providers/capa,./providers/eks |
/run cluster-test-suites TARGET_SUITES=./providers/capa/cilium-eni-mode |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
Oh No! 😱 At least one test suite has failed during the Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources: PIPELINE_RUN="pr-cluster-test-suites-444-cluster-test-suitesxj5jc"
NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
What this PR does
Towards: https://github.com/giantswarm/giantswarm/issues/29815
Checklist
Trigger e2e tests
/run cluster-test-suites